| am typing. I've re-read what I have typed to you and there is no mistake in what I am saying and I'm not contradicting myself. You are confused with what the low octane maps are actually for. When the system detects knock while the engine condition is within the knock zone, it WILL retard timing. This is true with ANY program, stock, JWT, JSPEC, my Stage3+ program. (with the exception of my own program in MY Z where there is no knock zone because I set all of those parameters with the 8th bit low; subtract 128 from those red values and you get the actual timing in degrees - but I eliminated the knock zone because my detonation sensor is not working AND I recently was freeing up processor cycles for some other code testing). All that happens when the car is in BOTH safety and normal mode. The low octane map ALSO has a knock zone. So even when it is in safety mode, it STILL listens for knock and will still retard timing if knock is detected even when in safety mode. It doesn't give up just because it is in safety mode. What my whole original post was getting at was the fact that the low octane maps are configured in a safer (and also less powerful) setup in my programming. I set it up this way a long time ago knowing this would be the case. Last night when it all came clear to me what the problem was, I was delighted to know that it was something I had alrady thought about before and configured the ECU for EXACTLY this reason. Its an indicator that something is wrong and it works for people who have boost controllers. For people with boost jets, it also works, but it mainly works because boost is lowered. For people with boost controllers they wouldn't know anything is wrong because the check engine light doesn't come on for a lot of different faults, but it will be in safety boost nonetheless.
[ ashleypowers.com ]
[ agpowers@bellsouth.net ] [ Zemulator Information Sheet ] When pigs dance, you better get it on video... "You never really learn to swear until you learn to drive."
-George Carlin
|
10:34:57 01/15/03
